Skip to content

Conversation

jog1t
Copy link
Contributor

@jog1t jog1t commented Oct 9, 2025

TL;DR

Created a reusable PendingRouteLayout component to standardize loading states across routes.

What changed?

  • Extracted the loading skeleton UI from the organization route into a new PendingRouteLayout component
  • Applied this component to multiple routes for consistent loading states:
    • Organization route
    • Project route
    • Namespace route
  • Updated imports to include H2 and Skeleton components where needed
  • Made a minor text change in the provider dropdown, changing "Coming soon!" to "Soon!" for Vercel integration

How to test?

  1. Navigate between different routes in the application
  2. Verify that loading states appear consistently across:
    • Organization pages
    • Project pages
    • Namespace pages
  3. Check that the loading skeleton UI displays correctly with proper spacing and layout

Why make this change?

This change improves code reusability by centralizing the loading UI into a single component rather than duplicating it across multiple routes. It ensures a consistent user experience during loading states throughout the application, making the interface feel more cohesive and polished.

Copy link

vercel bot commented Oct 9, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
rivet-cloud (staging) Ready Ready Preview Comment Oct 14, 2025 0:56am
rivet-inspector Ready Ready Preview Comment Oct 14, 2025 0:56am
2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
rivet-cloud Ignored Ignored Preview Oct 14, 2025 0:56am
rivet-site Ignored Ignored Preview Oct 14, 2025 0:56am

Copy link

claude bot commented Oct 9, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link
Contributor Author

jog1t commented Oct 9, 2025

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more


How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@jog1t jog1t mentioned this pull request Oct 9, 2025
@jog1t jog1t requested a review from NathanFlurry October 9, 2025 18:10
Copy link
Contributor

graphite-app bot commented Oct 9, 2025

Graphite Automations

"Test" took an action on this PR • (10/09/25)

1 assignee was added to this PR based on Kacper Wojciechowski's automation.

Copy link

pkg-pr-new bot commented Oct 9, 2025

Open in StackBlitz

npm i https://pkg.pr.new/rivet-dev/engine/@rivetkit/engine-runner@3145
npm i https://pkg.pr.new/rivet-dev/engine/@rivetkit/engine-runner-protocol@3145

commit: ac51843

Copy link

claude bot commented Oct 9, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link

claude bot commented Oct 9, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link

claude bot commented Oct 10, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link

claude bot commented Oct 12, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link

claude bot commented Oct 12, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link

claude bot commented Oct 13, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link

claude bot commented Oct 13, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link

claude bot commented Oct 13, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

@jog1t jog1t force-pushed the 10-09-fix_add_skeleton_remove_blinking_ branch from ec04e22 to ac51843 Compare October 14, 2025 00:52
Copy link

claude bot commented Oct 14, 2025

Claude encountered an error —— View job


I'll analyze this and get back to you.

Copy link
Contributor

graphite-app bot commented Oct 14, 2025

Merge activity

  • Oct 14, 4:19 AM UTC: NathanFlurry added this pull request to the Graphite merge queue.
  • Oct 14, 4:19 AM UTC: CI is running for this pull request on a draft pull request (#3186) due to your merge queue CI optimization settings.
  • Oct 14, 4:20 AM UTC: Merged by the Graphite merge queue via draft PR: #3186.

graphite-app bot pushed a commit that referenced this pull request Oct 14, 2025
### TL;DR

Created a reusable `PendingRouteLayout` component to standardize loading states across routes.

### What changed?

- Extracted the loading skeleton UI from the organization route into a new `PendingRouteLayout` component
- Applied this component to multiple routes for consistent loading states:
  - Organization route
  - Project route
  - Namespace route
- Updated imports to include `H2` and `Skeleton` components where needed
- Made a minor text change in the provider dropdown, changing "Coming soon!" to "Soon!" for Vercel integration

### How to test?

1. Navigate between different routes in the application
2. Verify that loading states appear consistently across:
   - Organization pages
   - Project pages
   - Namespace pages
3. Check that the loading skeleton UI displays correctly with proper spacing and layout

### Why make this change?

This change improves code reusability by centralizing the loading UI into a single component rather than duplicating it across multiple routes. It ensures a consistent user experience during loading states throughout the application, making the interface feel more cohesive and polished.
@graphite-app graphite-app bot closed this Oct 14, 2025
@graphite-app graphite-app bot deleted the 10-09-fix_add_skeleton_remove_blinking_ branch October 14, 2025 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants